Systems and methods for facilitating provisioning of internet protocol multimedia subsystem services

ABSTRACT

In some implementations, a network device (e.g., an Internet protocol multimedia subsystem (IMS) application server (IMS-AS) may receive, via a first communication interface, from a call session control function (CSCF) device, a request to register for an Internet protocol multimedia subsystem (IMS) service. The network device may provide via a second communication interface between the network device and a unified data management (UDM) device, and to the UDM device, a request for IMS service information associated with the IMS service. The network device may receive based on providing the request for IMS service information, via the second communication interface, and from the UDM device, IMS service information. The network device may cause, based on the IMS service information, the IMS service to be provided to a user device associated with the request to register for the IMS service.

RELATED APPLICATION

This application is a continuation of U.S. Pat. Application No.17/660,782, titled “SYSTEMS AND METHODS FOR FACILITATING PROVISIONING OFINTERNET PROTOCOL MULTIMEDIA SUBSYSTEM SERVICES,” filed Apr. 26, 2022,which is incorporated herein by reference in its entirety.

BACKGROUND

A user device may access Internet protocol (IP) multimedia subsystem(IMS) services via a core network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1E are diagrams of an example associated with facilitatingprovisioning of IMS services.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2 .

FIG. 4 is a flowchart of an example process relating to facilitatingprovisioning of IMS services.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A home subscriber server (HSS) of a fourth-generation (4G) network mayenable a user device (e.g., a mobile terminal or a user equipment (UE))to access IMS services. When a user device requests an IMS service(e.g., a voice-over-IP (VoIP) service, an IMS messaging service, and/orthe like), an IMS application server (IMS-AS) obtains information fromthe HSS in order to provide the IMS service to the user device. In afifth-generation (5G) network, the IMS-AS may communicate with a unifieddata management (UDM) device, via an HSS, to obtain the information inorder to provide the IMS service to the user device. Current techniquesmay co-locate the HSS with the UDM or integrate the HSS within the UDM.However, such arrangements still require the IMS-AS to query the HSS inorder to reach the UDM and obtain information for providing the IMSservice to the user device. Moreover, an HSS configured for a 4G networkdoes not support service-based interfaces, thus, a network provider maybe required to provide and maintain a first type of HSS for a 4G networkand a second type of HSS for a 5G network.

Consequently, current techniques for an IMS-AS to provide the IMSservice to the user device consume computing resources (e.g., processingresources, memory resources, communication resources, and/or powerresources, among other examples), networking resources, and/or otherresources associated with providing and maintaining two types of HSSsfor a 4G network and a 5G network, causing additional communicationsbetween the HSS and the UDM device to enable the IMS-As to communicatewith the UDM device, and/or the like.

Some implementations described herein provide a network device (e.g., anIMS-AS device) that facilitates provisioning of IMS services. Forexample, the IMS-AS device establishes a communication interface with aUDM device. The IMS-AS device may receive, via another communicationinterface and from a call session control function (CSCF) device, arequest to register for an IMS service. Accordingly, the IMS-AS devicemay provide, via the communication interface and to the UDM device, arequest for IMS service information associated with the IMS service. TheIMS-AS device may receive, based on providing the request for IMSservice information, via the communication interface, and from the UDMdevice, the IMS service information (e.g., that includes registrationdata associated with the IMS service, location data associated with theIMS service, authentication data associated with the IMS service, and/orsubscriber profile data associated with the IMS service). The IMS-ASdevice may thereby cause, based on the IMS service information, the IMSservice to be provided to a user device associated with the request toregister for the IMS service

In this way, the IMS-AS device facilitates provisioning of the IMSservices. For example, the IMS-AS device and the UDM device may each beenhanced to support a communication interface (e.g., a service-basedinterface) between the IMS-AS and the UDM device. The communicationinterface may be utilized to provide (e.g., directly provide) the IMSservice information to the IMS-AS device. The IMS-AS device may utilizeIMS service information to facilitate provisioning of the IMS service tothe user device. Thus, the IMS-AS device and the UDM device may conservecomputing resources, networking resources, and/or other resources thatwould have otherwise been consumed by providing and maintaining twotypes of HSSs for a 4G network and a 5G network, causing additionalcommunications between the HSS and the UDM device to enable the IMS-ASto communicate with the UDM device, and/or the like.

FIGS. 1A-1E are diagrams of an example 100 associated with facilitatingprovisioning of IMS services. As shown in FIGS. 1A-1E, example 100includes a user device (UD) 105, a radio access network (RAN) 110, and acore network 115 (e.g., a 5G core network). The core network 115 mayinclude a session management function (SMF)/user plane function (UPF), aP/I/S-CSCF (e.g., a proxy CSCF or P-CSCF, an interrogating CSCF orI-CSCF, and a serving CSCF or S-CSCF), a UDM device 120 (also referredto as the UDM 120), a unified data repository (UDR), and a networkresource function (NRF) device 125 (also referred to as the NRF 125). Asfurther shown in FIGS. 1A-1E, example 100 further includes an IMSnetwork 130, which may include an IMS-AS device 135 (also referred to asthe IMS-AS 135). Further details of the user device 105, the RAN 110,the core network 115, the SMF/UPF, the P/I/S-CSCF, the UDM 120, the UDR,the NRF 125, and the IMS-AS 135, are provided elsewhere herein.

As shown in FIG. 1A, the user device 105 may communicate with the corenetwork 115 via the RAN 110. The IMS-AS 135 may communicate with theP/I/S-CSCF and the NRF 125 via communication interfaces. As furthershown in FIG. 1A, a new communication interface Ny (e.g., aservice-based interface or SBI) may be established between IMS-AS 135and the UDM 120 (e.g., that directly connects the IMS-AS 135 and the UDM120) to enable the IMS-AS 135 to communicate (e.g., directlycommunicate) with the UDM 120. The UDM 120 and the IMS-AS 135 may beenhanced to establish and support the SBI Ny interface, and may utilizethe SBI Ny to communicate one or more messages related to IMS serviceinformation, as described below in connection with FIGS. 1B-1E. Asfurther shown in FIG. 1A, the UDM 120 may communicate with the UDR via acommunication interface Nudr. The UDR (also referred to as a UDR device)may include a data structure (e.g., a database, a table, a list, and/orthe like) that stores the subscriber information.

As shown in FIG. 1B, and by reference number 140, the P-CSCF mayreceive, from the user device 105, a request (e.g., an invite request)to register for an IMS service, such as an IMS voice service (e.g., aVoIP service, such as a voice over new radio (VoNR) service), an IMSvideo service (e.g., a video over new radio (ViNR) service), or an IMSmessaging service (e.g., a rich communication services (RCS) service).For example, the user device 105 may execute an IMS messagingapplication and the IMS messaging application may generate a request toregister an IMS messaging service. The request to register may includeregistration information associated with the user device 105, such aninternational mobile subscriber identity (IMSI) of the user device 105,a mobile station international subscriber directory number (MSISDN ofthe user device 105, an international mobile equipment identity (IMEI)of the user device 105, a subscription permanent identifier (SUPI) ofthe user device 105, a generic public subscription identifier (GPSI) ofthe user device 105, and/or a permanent equipment identifier (PEI) ofthe user device. The user device 105 may provide the request to registerfor the IMS messaging service to the P-CSCF via the RAN 110. The P-CSCFmay receive the request to register from the RAN 110. The P-CSCF mayinclude a session initiation protocol (SIP) proxy that is a first pointof contact for the user device 105 in the core network 115. All SIPtraffic to and from the user device 105 may travel through the P-CSCF.

As further shown in FIG. 1B, and by reference number 145, the P-CSCF mayprovide the request to register for the IMS service to the S-CSCF. TheS-CSCF may enable requests to be routed to a correct IMS-AS associatedwith the IMS service, since there may be more than one IMS-AS within theIMS network 130. Accordingly, as shown by reference number 150, theS-CSCF may provide the request to register to the IMS-AS 135 (e.g., thatis configured to provide, or to facilitate provision of, the IMS serviceto the user device 105). For example, the S-CSCF may provide, via acommunication interface between the S-CSCF and the IMS-AS 135, therequest to register (e.g., that includes the registration information)to the IMS-AS 135, and the IMS-AS 135 may receive the request toregister.

As shown in FIG. 1C, and by reference number 155, the IMS-AS 135 mayprovide, to the NRF 125, a request for identification of a UDM for theIMS service. For example, the IMS-AS 135 may generate the request foridentification of the UDM for the IMS service based on receiving therequest to register. In some implementations, the request foridentification may include a request for identification of a networkfunction (e.g., the UDM 120) that can facilitate provisioning of the IMSservice to the user device 105. The request for identification mayinclude at least some of the registration information (e.g., at leastone of the IMSI of the user device 105, the MSISDN of the user device105, the IMEI of the user device 105, the SUPI of the user device 105,or the GPSI of the user device 105). The IMS-AS 135 may provide therequest for identification to the NRF 125 (e.g., via a communicationinterface between the IMS-AS 135 and the NRF 125), and the NRF 125 mayreceive the request for identification.

As further shown in FIG. 1C, and by reference number 160, the IMS-AS 135may receive, from the NRF 125, the identification of the UDM 120 for theIMS service. For example, the NRF 125 may determine the identificationof the UDM 120 based on the request for identification. The NRF 125 mayidentify the UDM 120 since the UDM 120 may be associated with the userdevice 105 and/or the IMS service requested by the user device 105. TheNRF 125 may provide the identification of the UDM 120 to the IMS-AS 135(e.g., via the communication interface between the IMS-AS 135 and theNRF 125) and the IMS-AS 135 may receive the identification of the UDM120 for the IMS service.

As shown in FIG. 1D, and by reference number 165, the IMS-AS 135 mayprovide, to the UDM 120, a request for IMS service informationassociated with the IMS service. The IMS-AS 135 may generate the requestfor IMS service information based on receiving the request to registerfor the IMS service from the S-CSCF. The request for IMS serviceinformation may include at least some of the registration information(e.g., at least one of the IMSI of the user device 105, the MSISDN ofthe user device 105, the IMEI of the user device 105, the SUPI of theuser device 105, or the GPSI of the user device 105). The IMS-AS 135 mayprovide the request for IMS service information to the UDM 120 (e.g.,via the communication interface Ny between the IMS-AS 135 and the UDM120), and the UDM 120 may receive the request for IMS serviceinformation.

As further shown in FIG. 1D, and by reference number 170, the IMS-AS 135may receive, from the UDM 120, IMS service information associated withthe IMS service based on the request for IMS service information. Forexample, the UDR may store the IMS service information associated withthe IMS service. The UDM 120 may retrieve, based on the request for IMSservice information and from the UDR, the IMS service informationassociated with the IMS service. The UDM 120 may provide the IMS serviceinformation retrieved from the UDR to the IMS-AS 135 (e.g., via thecommunication interface Ny between the IMS-AS 135 and the UDM 120), andthe IMS-AS 135 may receive the IMS service information.

The IMS service information may include, for example, registration dataassociated with the IMS service, location data associated with the IMSservice, authentication data associated with the IMS service, and/orsubscriber profile data associated with the IMS service. Theregistration data may include data identifying, for example, users(e.g., associated with user devices 105) that are registered to utilizethe IMS service, and/or user devices 105 that are registered to utilizethe IMS service. The location data may include data identifying, forexample, locations of user devices 105 that are registered to utilizethe IMS service and/or a location of the IMS service. The authenticationdata may include data identifying, for example, authenticationcredentials of users of user devices 105 that are registered to utilizethe IMS service and/or authentication credentials of the IMS service.The subscriber profile data associated with the IMS service may includedata identifying, for example, subscriber profiles of users of userdevices 105 that are registered to utilize the IMS service.

As further shown in FIG. 1D, and by reference number 175, the IMS-AS 135may cause the IMS service to be provided to the user device 105 (e.g.,based on the IMS service information). For example, the IMS-AS 135 maydetermine, based on the registration data associated with the IMSservice, the location data associated with the IMS service, theauthentication data associated with the IMS service, and/or thesubscriber profile data associated with the IMS service that is includedin the IMS service information, that the user device 105 is to receivethe IMS service and that the IMS-AS 135 is capable of providing, orfacilitating provisioning of, the IMS service. Accordingly, the IMS-AS135 may provide, or may facilitate provisioning of, the IMS service tothe user device 105.

As shown in FIG. 1E, and by reference number 180, the IMS-AS 135 and theUDM 120 may communicate one or more messages related to the IMS serviceinformation (e.g., based on the IMS-AS 135 causing the IMS service to beprovided to the user device 105).

In an example, the IMS-AS 135 may provide, to the UDM 120, a request tosubscribe to IMS session information updates. The IMS-AS 135 maygenerate the request to subscribe to IMS session information updatesbased on the IMS-AS 135 causing the IMS service to be provided to theuser device. The IMS-AS 135 may provide the request to subscribe to IMSsession information updates to the UDM 120 (e.g., via the communicationinterface Ny between the IMS-AS 135 and the UDM 120), and the UDM 120may receive the request to subscribe to IMS session information updates.The request to subscribe to IMS session information updates may specifyone or more parameters of the IMS session information to monitor forupdates and/or a reporting frequency for providing updates to the IMS-AS135 (e.g., upon detection of an update to the one or more parameters orat a particular time interval after detection of the update).

Accordingly, the UDM 120 may monitor, based on the request to subscribeto IMS session information updates, the UDR for one or more changes tothe one or more parameters of the IMS service information. Afterdetecting the one or more changes, the UDM 120 may provide (e.g., basedon the reporting frequency indicated by the request to subscribe to IMSsession information updates) updated IMS service information retrievedfrom the UDR to the IMS-AS 135 (e.g., via the communication interface Nybetween the IMS-AS 135 and the UDM 120), and the IMS-AS 135 may receivethe updated IMS service information.

As another example, the IMS-AS 135 may provide, to the UDM 120, arequest to modify a subscription to IMS session information updates. TheIMS-AS 135 may generate the request to modify a subscription to IMSsession information updates after sending the request to subscribe toIMS session information updates. The IMS-AS 135 may provide the requestto modify a subscription to IMS session information updates to the UDM120 (e.g., via the communication interface Ny between the IMS-AS 135 andthe UDM 120), and the UDM 120 may receive the request to modify asubscription to IMS session information updates. The request to modify asubscription to IMS session information updates may indicate one or moreparameters (e.g., that are at least partially different than the one ormore parameters indicated by the request to subscribe to IMS sessioninformation updates) of the IMS session information to monitor forupdates and/or a reporting frequency for providing updates to the IMS-AS135 (e.g., that is different than the reporting frequency indicated bythe request to subscribe to IMS session information updates).

Accordingly, the UDM 120 may monitor, based on the request to modify asubscription to IMS session information updates, the UDR for one or morechanges to the one or more parameters of the IMS service information.After detecting the one or more changes, the UDM 120 may provide (e.g.,based on the reporting frequency indicated by the request to modify asubscription to IMS session information updates) additional updated IMSservice information retrieved from the UDR to the IMS-AS 135 (e.g., viathe communication interface Ny between the IMS-AS 135 and the UDM 120),and the IMS-AS 135 may receive the updated IMS service information.

As an additional example, the IMS-AS 135 may provide, to the UDM 120, arequest to cancel a subscription to IMS session information updates. TheIMS-AS 135 may generate the request to cancel a subscription to IMSsession information updates after sending the request to subscribe toIMS session information updates. The IMS-AS 135 may provide the requestto cancel a subscription to IMS session information updates to the UDM120 (e.g., via the communication interface Ny between the IMS-AS 135 andthe UDM 120), and the UDM 120 may receive the request to cancel asubscription to IMS session information updates. The request to cancel asubscription to IMS session information updates may indicate that theUDM 120 is to cease monitoring for updates to the IMS sessioninformation. Accordingly, the UDM 120 may cease monitoring, based on therequest to cancel a subscription to IMS session information updates, theUDR for changes to the IMS service information. In this way, the UDM 120is prevented from sending additional updated subscriber information tothe IMS-AS 135.

In another example, the IMS-AS 135 may identify a change to one or moreparameters of the IMS service information. For example, based on causingthe IMS service to be provided to the user device, the IMS-AS 135 maydetermine that a location associated with the user device 105 and/or alocation associated with the IMS service has changed. Accordingly, theIMS-AS 135 may provide information indicating the change to the one ormore parameters of the IMS service information (e.g., via thecommunication interface Ny between the IMS-AS 135 and the UDM 120), andthe UDM 120 may receive the information indicating the change to the oneor more parameters of the IMS service information. The UDM 120 mayupdate, based on the information indicating the change to the one ormore parameters of the IMS service information, the IMS serviceinformation in the UDR.

As further shown in FIG. 1E, and by reference number 185, the IMS-AS 135may cause modification of one or more parameters associated withproviding the IMS service to the user device 105. For example, theIMS-AS 135 may determine, based on the updated subscriber information,the additional updated subscriber information, and/or the informationindicating the change to the one or more parameters of the IMS serviceinformation (as described in the examples above), that the one or moreparameters associated with providing the IMS service to the user device105 need to be modified. Accordingly, the IMS-AS 135 may causemodification of the one or more parameters associated with providing theIMS service to the user device 105.

As indicated above, FIGS. 1A-1E are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 1A-1E.The number and arrangement of devices shown in FIGS. 1A-1E are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged devices than thoseshown in FIGS. 1A-1E. Furthermore, two or more devices shown in FIGS.1A-1E may be implemented within a single device, or a single deviceshown in FIGS. 1A-1E may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 1A-1E may perform one or more functionsdescribed as being performed by another set of devices shown in FIGS.1A-1E.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2 ,the example environment 200 may include the user device 105, the RAN110, the core network 115, the IMS network 130, and a data network 255.Devices and/or networks of the example environment 200 may interconnectvia wired connections, wireless connections, or a combination of wiredand wireless connections.

The user device 105 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information, such asinformation described herein. For example, the user device 105 caninclude a mobile phone (e.g., a smart phone or a radiotelephone), alaptop computer, a tablet computer, a desktop computer, a handheldcomputer, a gaming device, a wearable communication device (e.g., asmart watch or a pair of smart glasses), a mobile hotspot device, afixed wireless access device, customer premises equipment, an autonomousvehicle, or a similar type of device.

The RAN 110 may support, for example, a cellular radio access technology(RAT). The RAN 110 may include one or more base stations (e.g., basetransceiver stations, radio base stations, node Bs, eNodeBs (eNBs),gNodeBs (gNBs), base station subsystems, cellular sites, cellulartowers, access points, transmit receive points (TRPs), radio accessnodes, macrocell base stations, microcell base stations, picocell basestations, femtocell base stations, or similar types of devices) andother network entities that can support wireless communication for theuser device 105. The RAN 110 may transfer traffic between the userdevice 105 (e.g., using a cellular RAT), one or more base stations(e.g., using a wireless interface or a backhaul interface, such as awired backhaul interface), and/or the core network 115. The RAN 110 mayprovide one or more cells that cover geographic areas.

In some implementations, the RAN 110 may perform scheduling and/orresource management for the user device 105 covered by the RAN 110(e.g., the user device 105 covered by a cell provided by the RAN 110).In some implementations, the RAN 110 may be controlled or coordinated bya network controller, which may perform load balancing, network-levelconfiguration, and/or other operations. The network controller maycommunicate with the RAN 110 via a wireless or wireline backhaul. Insome implementations, the RAN 110 may include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, the RAN 110 may perform network control,scheduling, and/or network management functions (e.g., for uplink,downlink, and/or sidelink communications of the user device 105 coveredby the RAN 110).

In some implementations, the core network 115 may include an examplefunctional architecture in which systems and/or methods described hereinmay be implemented. For example, the core network 115 may include anexample architecture of a 5G next generation (NG) core network includedin a 5G wireless telecommunications system. While the examplearchitecture of the core network 115 shown in FIG. 2 may be an exampleof a service-based architecture, in some implementations, the corenetwork 115 may be implemented as a reference-point architecture and/ora 4G core network, among other examples.

As shown in FIG. 2 , the core network 115 may include a number offunctional elements. The functional elements may include, for example, anetwork slice selection function (NSSF) 205, a network exposure function(NEF) 210, an authentication server function (AUSF) 215, the UDM 120, apolicy control function (PCF) 220, an application function (AF) 225, anaccess and mobility management function (AMF) 230, a session managementfunction (SMF) 235, a user plane function (UPF) 240, and the NRF 125.These functional elements may be communicatively connected via a messagebus 245. Each of the functional elements shown in FIG. 2 is implementedon one or more devices associated with a wireless telecommunicationssystem. In some implementations, one or more of the functional elementsmay be implemented on physical devices, such as an access point, a basestation, and/or a gateway. In some implementations, one or more of thefunctional elements may be implemented on a computing device of a cloudcomputing environment.

The NSSF 205 includes one or more devices that select network sliceinstances for the user device 105. By providing network slicing, theNSSF 205 allows an operator to deploy multiple substantially independentend-to-end networks potentially with the same infrastructure. In someimplementations, each slice may be customized for different services.

The NEF 210 includes one or more devices that support exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services.

The AUSF 215 includes one or more devices that act as an authenticationserver and support the process of authenticating the user device 105 inthe wireless telecommunications system.

The UDM 120 includes one or more devices that store user data andprofiles in the wireless telecommunications system. The UDM 120 mayreceive, generate, store, process, and/or provide information, such asIMS service information described herein. The UDM 120 may be used forfixed access and/or mobile access in the core network 115.

The PCF 220 includes one or more devices that provide a policy frameworkthat incorporates network slicing, roaming, packet processing, and/ormobility management, among other examples.

The AF 225 includes one or more devices that support applicationinfluence on traffic routing, access to the NEF 210, and/or policycontrol, among other examples.

The AMF 230 includes one or more devices that act as a termination pointfor non-access stratum (NAS) signaling and/or mobility management, amongother examples.

The SMF 235 includes one or more devices that support the establishment,modification, and release of communication sessions in the wirelesstelecommunications system. For example, the SMF 235 may configuretraffic steering policies at the UPF 240 and/or may enforce userequipment IP address allocation and policies, among other examples.

The UPF 240 includes one or more devices that serve as an anchor pointfor intraRAT and/or interRAT mobility. The UPF 240 may apply rules topackets, such as rules pertaining to packet routing, traffic reporting,and/or handling user plane quality of service (QoS), among otherexamples.

The NRF 125 includes one or more devices that provide a single record ofall network functions available in the core network 115, together with aprofile of each network function and services supported by each networkfunction. The NRF 125 may allow other network functions to subscribe to,and get notified about, registration in the NRF 125 of new networkfunction instances. In addition to maintaining profiles, the NRF 125also supports service discovery functions, enabling other networkfunctions to obtain information regarding available network functionsthat can support specific services.

The message bus 245 represents a communication structure forcommunication among the functional elements. In other words, the messagebus 245 may permit communication between two or more functionalelements.

The IMS network 130 may include various types of IMS networkarchitectures associated with providing IMS services, such as mediastreaming, voice over IP (VoIP), rich communication services (RCS),and/or the like. The IMS network 130 may include an IMS core of aplurality of functional elements (e.g., that includes the IMS-AS 135, aP/I/S-CSCF 250, a telephony application server (TAS), a multimediaresource function control (MRFC), a short message service function(SMSF), and/or a secondary cell group (SCG)). In some implementations,The IMS network 130 can be implemented on physical devices, such as agateway, a mobility management entity, and/or the like. In someimplementations, the hardware and/or software implementing the IMSnetwork 130 can be virtualized (e.g., through use of network functionvirtualization and/or software-defined networking), thereby allowing forthe use of composable infrastructure when implementing the IMS network130. In this way, networking, storage, and compute resources can beallocated to implement the functions of the IMS network 130 in aflexible manner as opposed to relying on dedicated hardware and softwareto implement these functions.

The IMS-AS 135 includes one or more devices capable of receiving,generating, storing, processing, providing, and/or routing informationassociated with an IMS service, as described elsewhere herein. TheIMS-AS 135 may include a communication device and/or a computing device.For example, the IMS-AS 135 may include a server, such as an applicationserver, a client server, a web server, a database server, a host server,a proxy server, a virtual server (e.g., executing on computinghardware), or a server in a cloud computing system. In someimplementations, the IMS-AS 135 includes computing hardware used in acloud computing environment.

The P/I/S-CSCF 250 includes one or more devices that manage allsignaling from an end user to services and other networks. TheP/I/S-CSCF 250 may control both fixed and mobile IMSs, may allocateapplication servers, may establish emergency connections, and maycontrol communication with other networks. The P/I/S/-CSCF 250 mayinclude a proxy-CSCF (P-CSCF), an interrogating-CSCF (I-CSCF), and aserving-CSCF (S-CSCF).

The data network 255 includes one or more wired and/or wireless datanetworks. For example, the data network 255 may include an IMS, a publicland mobile network (PLMN), a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), a private network suchas a corporate intranet, an ad hoc network, the Internet, a fiberoptic-based network, a cloud computing network, a third party servicesnetwork, an operator services network, and/or a combination of these orother types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of theexample environment 200 may perform one or more functions described asbeing performed by another set of devices of the example environment200.

FIG. 3 is a diagram of example components of a device 300, which maycorrespond to the user device 105, the RAN 110, the UDM 120, the NSSF205, the NEF 210, the AUSF 215, the PCF 220, the AF 225, the AMF 230,the SMF 235, the UPF 240, the NRF 125, the P/I/S-CSCF 250, and/or theIMS-AS 135. In some implementations, the user device 105, the RAN 110,the UDM 120, the NSSF 205, the NEF 210, the AUSF 215, the PCF 220, theAF 225, the AMF 230, the SMF 235, the UPF 240, the NRF 125, theP/I/S-CSCF 250, and/or the IMS-AS 135 include one or more devices 300and/or one or more components of device 300. As shown in FIG. 3 , device300 may include a bus 310, a processor 320, a memory 330, an inputcomponent 340, an output component 350, and a communication component360.

Bus 310 includes one or more components that enable wired and/orwireless communication among the components of device 300. Bus 310 maycouple together two or more components of FIG. 3 , such as via operativecoupling, communicative coupling, electronic coupling, and/or electriccoupling. Processor 320 includes a central processing unit, a graphicsprocessing unit, a microprocessor, a controller, a microcontroller, adigital signal processor, a field-programmable gate array, anapplication-specific integrated circuit, and/or another type ofprocessing component. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. In someimplementations, processor 320 includes one or more processors capableof being programmed to perform one or more operations or processesdescribed elsewhere herein.

Memory 330 includes volatile and/or nonvolatile memory. For example,memory 330 may include random access memory (RAM), read only memory(ROM), a hard disk drive, and/or another type of memory (e.g., a flashmemory, a magnetic memory, and/or an optical memory). Memory 330 mayinclude internal memory (e.g., RAM, ROM, or a hard disk drive) and/orremovable memory (e.g., removable via a universal serial busconnection). Memory 330 may be a non-transitory computer-readablemedium. Memory 330 stores information, instructions, and/or software(e.g., one or more software applications) related to the operation ofdevice 300. In some implementations, memory 330 includes one or morememories that are coupled to one or more processors (e.g., processor320), such as via bus 310.

Input component 340 enables device 300 to receive input, such as userinput and/or sensed input. For example, input component 340 may includea touch screen, a keyboard, a keypad, a mouse, a button, a microphone, aswitch, a sensor, a global positioning system sensor, an accelerometer,a gyroscope, and/or an actuator. Output component 350 enables device 300to provide output, such as via a display, a speaker, and/or alight-emitting diode. Communication component 360 enables device 300 tocommunicate with other devices via a wired connection and/or a wirelessconnection. For example, communication component 360 may include areceiver, a transmitter, a transceiver, a modem, a network interfacecard, and/or an antenna.

Device 300 may perform one or more operations or processes describedherein. For example, a non-transitory computer-readable medium (e.g.,memory 330) may store a set of instructions (e.g., one or moreinstructions or code) for execution by processor 320. Processor 320 mayexecute the set of instructions to perform one or more operations orprocesses described herein. In some implementations, execution of theset of instructions, by one or more processors 320, causes the one ormore processors 320 and/or the device 300 to perform one or moreoperations or processes described herein. In some implementations,hardwired circuitry is used instead of or in combination with theinstructions to perform one or more operations or processes describedherein. Additionally, or alternatively, processor 320 may be configuredto perform one or more operations or processes described herein. Thus,implementations described herein are not limited to any specificcombination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 3 are provided asan example. Device 300 may include additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 3 . Additionally, or alternatively, a set ofcomponents (e.g., one or more components) of device 300 may perform oneor more functions described as being performed by another set ofcomponents of device 300.

FIG. 4 is a flowchart of an example process 400 for facilitatingprovisioning of IMS services. In some implementations, one or moreprocess blocks of FIG. 4 may be performed by a network device (e.g., theIMS-AS 135). In some implementations, one or more process blocks of FIG.4 may be performed by another device or a group of devices separate fromor including the network device, such as UDM (e.g., the UDM 120), an NRF(e.g., the NRF 125), a CSCF (e.g., the P/I/S-CSCF 250), and/or the like.Additionally, or alternatively, one or more process blocks of FIG. 4 maybe performed by one or more components of the device 300, such as theprocessor 320, the memory 330, the input component 340, the outputcomponent 350, and/or the communication component 360.

As shown in FIG. 4 , process 400 may include receiving a request toregister (block 410). For example, the network device may receive via afirst communication interface, from a call session control function(CSCF) device, a request to register for an Internet protocol multimediasubsystem (IMS) service, as described above. In some implementations,the request to register includes registration information that comprisesat least one of an international mobile subscriber identity of the userdevice, a mobile station international subscriber directory number ofthe user device, an international mobile equipment identity of the userdevice, a subscription permanent identifier of the user device, ageneric public subscription identifier of the user device, or apermanent equipment identifier of the user device.

As further shown in FIG. 4 , process 400 may include providing a requestfor IMS service information (block 420). For example, the network devicemay provide via a second communication interface between the networkdevice and a unified data management (UDM) device, and to the UDMdevice, a request for IMS service information associated with the IMSservice, as described above. The second communication interface mayinclude a service-based interface between the network device and the UDMdevice.

As further shown in FIG. 4 , process 400 may include receiving IMSservice information (block 430). For example, the network device mayreceive based on providing the request for IMS service information, viathe second communication interface, and from the UDM device, IMS serviceinformation, as described above. In some implementations, the IMSservice information comprises at least one of data associated with theIMS service, location data associated with the IMS service, dataassociated with the IMS service, or profile data associated with the IMSservice.

As further shown in FIG. 4 , process 400 may include causing an IMSservice to be provided (block 440). For example, the network device maycause, based on the IMS service information, the IMS service to beprovided to a user device associated with the request to register forthe IMS service, as described above. The IMS service may include atleast one of: an IMS voice service, an IMS video service, or an IMSmessaging service.

In some implementations, process 400 includes communicating, based oncausing the IMS service to be provided to the user device, via thesecond communication interface, and with the UDM device, one or moremessages related to the IMS service information. For example, process400 includes providing, based on causing the IMS service to be providedto the user device, via the second communication interface, and to theUDM device, a request to subscribe to IMS service information updates,receiving, based on sending the request to subscribe to IMS serviceinformation updates, via the second communication interface, and fromthe UDM device, updated IMS service information, and causing, based onthe updated IMS service information, modification of one or moreparameters associated with providing the IMS service to the user device.

As another example, process 400 includes providing, after receiving theupdated IMS service information, via the second communication interface,and to the UDM device, a request to modify a subscription to IMS serviceinformation updates, receiving, based on sending the request to modify asubscription to IMS service information updates, via the secondcommunication interface, and from the UDM device, additional updated IMSservice information, and causing, based on the additional updated IMSservice information, additional modification of the one or moreparameters associated with providing the IMS service to user device.

In an additional example, process 400 includes sending, after receivingthe updated IMS service information, via the second communicationinterface, and to the UDM device, a request to cancel a subscription toIMS service information updates, wherein sending the request to cancel asubscription to IMS service information updates is to prevent the UDMdevice from sending additional updated subscriber information to thenetwork device. In another example, process 400 includes identifying,based on causing the IMS service to be provided to the user device, achange to one or more parameters of the IMS service information, andsending, via the second communication interface, and to the UDM device,information indicating the change.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Itwill be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code - it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set. As used herein, aphrase referring to “at least one of” a list of items refers to anycombination of those items, including single members. As an example, “atleast one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c,and a-b-c, as well as any combination with multiple of the same item.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, or a combination of related and unrelateditems), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

In the preceding specification, various example embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

What is claimed is:
 1. A method, comprising: receiving, by a network device, via a first communication interface, and from a first device, a request to register for an Internet protocol multimedia subsystem (IMS) service; providing, by the network device, via a second communication interface between the network device and a second device, and to the second device, a request for IMS service information associated with the IMS service; and causing, by the network device and based on IMS service information received from the second device, the IMS service to be provided to a user device associated with the request to register for the IMS service.
 2. The method of claim 1, wherein the request to register for the IMS service comprises one or more of: a subscription permanent identifier of the user device, a generic public subscription identifier of the user device, or a permanent equipment identifier.
 3. The method of claim 1, wherein the IMS service information comprises one or more of: registration data associated with the IMS service, location data associated with the IMS service, authentication data associated with the IMS service, or subscriber profile data associated with the IMS service.
 4. The method of claim 1, further comprising: providing, based on causing the IMS service to be provided to the user device, via the second communication interface, and to the second device, a request to subscribe to IMS service information updates; receiving, based on sending the request to subscribe to IMS service information updates, via the second communication interface, and from the second device, updated IMS service information; and causing, based on the updated IMS service information, modification of one or more parameters associated with providing the IMS service to the user device.
 5. The method of claim 4, further comprising: providing, via the second communication interface and based on receiving the updated IMS service information, a request to modify a subscription to IMS service information updates to the second device; receiving, via the second communication interface and based on sending the request to modify the subscription to the IMS service information updates, additional updated IMS service information from the second device; and causing, based on the additional updated IMS service information, an additional modification of the one or more parameters associated with providing the IMS service to the user device.
 6. The method of claim 4, further comprising: providing, via the second communication interface and based on receiving the updated IMS service information, a request to cancel a subscription to IMS service information updates to the second device, wherein additional updated subscriber information is not received by the network device based on providing the request to cancel the subscription to the IMS service information updates to the second device.
 7. The method of claim 1, further comprising: identifying, based on causing the IMS service to be provided to the user device, a change to one or more parameters of the IMS service information; and sending, via the second communication interface and to the second device, information indicating the change.
 8. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a network device, cause the network device to: receive via a first communication interface, and from a first device, a request to register for an Internet protocol multimedia subsystem (IMS) service; provide via a second communication interface between the network device and a second device, and to the second device, a request for IMS service information associated with the IMS service; and cause, based on IMS service information received from the second device, the IMS service to be provided to a user device associated with the request to register for the IMS service.
 9. The non-transitory computer-readable medium of claim 8, wherein the request to register for the IMS service comprises one or more of: a subscription permanent identifier of the user device, a generic public subscription identifier of the user device, or a permanent equipment identifier.
 10. The non-transitory computer-readable medium of claim 8, wherein the IMS service information comprises one or more of: data associated with the IMS service, location data associated with the IMS service, data associated with the IMS service, or profile data associated with the IMS service.
 11. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions further cause the network device to: provide, based on causing the IMS service to be provided to the user device, via the second communication interface, and to the second device, a request to subscribe to IMS service information updates; receive, based on sending the request to subscribe to IMS service information updates, via the second communication interface, and from the second device, updated IMS service information; and cause, based on the updated IMS service information, modification of one or more parameters associated with providing the IMS service to the user device.
 12. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions further cause the network device to: provide, via the second communication interface and based on receiving the updated IMS service information, a request to modify a subscription to IMS service information updates to the second device; receive, via the second communication interface and based on sending the request to modify the subscription to the IMS service information updates, additional updated IMS service information from the second device; and cause, based on the additional updated IMS service information, an additional modification of the one or more parameters associated with providing the IMS service to the user device.
 13. The non-transitory computer-readable medium of claim 11, wherein the one or more instructions further cause the network device to: provide, via the second communication interface and based on receiving the updated IMS service information, a request to cancel a subscription to IMS service information updates to the second device, wherein additional updated subscriber information is not received by the network device based on providing the request to cancel the subscription to the IMS service information updates to the second device.
 14. The non-transitory computer-readable medium of claim 8, wherein the one or more instructions further cause the network device to: identify, based on causing the IMS service to be provided to the user device, a change to one or more parameters of the IMS service information; and send, via the second communication interface and to the second device, information indicating the change.
 15. A network device, comprising: one or more processors configured to: receive via a first communication interface, and from a first device, a request to register for an Internet protocol multimedia subsystem (IMS) service; provide via a second communication interface between the network device and a second device, and to the second device, a request for IMS service information associated with the IMS service; and cause, based on IMS service information received from the second device, the IMS service to be provided to a user device associated with the request to register for the IMS service.
 16. The network device of claim 15, wherein the request to register for the IMS service comprises one or more of: a subscription permanent identifier of the user device, a generic public subscription identifier of the user device, or a permanent equipment identifier; and wherein the IMS service information comprises one or more of: data associated with the IMS service, location data associated with the IMS service, data associated with the IMS service, or profile data associated with the IMS service.
 17. The network device of claim 15, wherein the one or more processors are further configured to: provide, based on causing the IMS service to be provided to the user device, via the second communication interface, and to the second device, a request to subscribe to IMS service information updates; receive, based on sending the request to subscribe to IMS service information updates, via the second communication interface, and from the second device, updated IMS service information; and cause, based on the updated IMS service information, modification of one or more parameters associated with providing the IMS service to the user device.
 18. The network device of claim 17, wherein the one or more processors are further configured to: provide, via the second communication interface and based on receiving the updated IMS service information, a request to modify a subscription to IMS service information updates to the second device; receive, via the second communication interface and based on sending the request to modify the subscription to the IMS service information updates, additional updated IMS service information from the second device; and cause, based on the additional updated IMS service information, an additional modification of the one or more parameters associated with providing the IMS service to the user device.
 19. The network device of claim 17, wherein the one or more processors are further configured to: provide, via the second communication interface and based on receiving the updated IMS service information, a request to cancel a subscription to IMS service information updates to the second device, wherein additional updated subscriber information is not received by the network device based on providing the request to cancel the subscription to the IMS service information updates to the second device.
 20. The network device of claim 15, wherein the one or more processors are further configured to: identify, based on causing the IMS service to be provided to the user device, a change to one or more parameters of the IMS service information; and send, via the second communication interface and to the second device, information indicating the change. 